Electronic device monitoring method, electronic device, computer, and program thereof

ABSTRACT

Processing relating to maintenance of a monitoring subject device is performed by detecting by a computer an IP address of an electronic device connected to a LAN, automatically referring to communication protocol specification data indicating a communication protocol with the electronic device indicated in remote maintenance management data provided in advance or obtained from the electronic device, and performing a communication with the electronic device by using said communication protocol and the IP address indicated by the communication protocol specification data.

TECHNICAL FIELD

[0001] The present invention relates to an electronic device monitoringmethod, an electronic device, a computer and the program for performingprocessing for monitoring and maintenance of an electronic deviceconnected via a network, such as a domestic LAN and the Internet, etc.

BACKGROUND ART

[0002] In a TCP/IP network system, a condition of an electronic devices,such as a rooter and a computer, connected to a network is monitored andcontrolled via the network, for example, by using the SNMP (SimpleNetwork Management Protocol).

[0003] In some of the TCP/IP network systems, a computer operatesmonitoring and maintenance of an electronic device, etc. via a networkby using the HTTP (HyperText Transfer Protocol), the FTP (File TransferProtocol) and the Telenet, etc. being high in security comparing withthe SNMP.

[0004] Conventionally, after a computer obtains data of an electronicdevice in an operating state by using the SNMP protocol, a userseparately starts up a Web browser and obtains information, such as anIP address of the electronic device, a communication protocol forcommunicating with the electronic devices, an access path (URL: UniformResource Locator) in a memory region of the electronic device, etc. tocommunicate with other electronic devices and to perform communicationand processing relating to maintenance of the electronic device.

[0005] The communication protocol used by the electronic device for itsmaintenance differs in some cases depending on respective electronicdevices.

[0006] In that case, if an administrator of the computer as a monitoringdevice sets to the computer communication protocols used fornotifications between respective electronic devices, the load on theadministrator becomes heavy, which is disadvantageous.

[0007] Also, as explained above, conventionally, a process of obtainingan operating condition of an electronic device 3 by using the SNMPprotocol and a process of maintenance of the electronic device 3 byusing the Web browser have to be performed separately. Thus, there is aproblem that monitoring and maintenance cannot be performed integrallyand a load on the user is large.

[0008] In the SNMP communication, when abnormality or an event arises inthe electronic device, the electronic device generates a Trap to notifythe state to the computer.

[0009] For that purpose, it is necessary that an IP address of thecomputer to which the Trap is transmitted is set to the electronicdevice.

[0010] Conventionally, the user sets the IP address as the transmissiondestination of the Trap by means of inputting to the electronic device.

[0011] As explained above, however, there is a problem that it is timeconsuming and inconvenient for the user to input to the electronicdevice the IP address as a transmission destination of the Trap.

[0012] Also, when the electronic device is portable and connected to aplurality of computers, the user has to input to the electronic devicethe IP address as a transmission destination of the Trap each time,which is particularly inconvenient.

[0013] When the Ipv6 will be widely used in the future, it isanticipated that household electronic appliances and portable terminaldevices utilizing the IP protocol will increase, but it is reluctant todo the time consuming setting works when using the SNMP in theelectronic devices.

DISCLOSURE OF INVENTION

[0014] The present invention was made in consideration on the aboveproblems and has as an object thereof to provide an electronic devicemonitoring method, an electronic device, a computer and its programcapable of automatically setting to a computer a communication protocolused between the computer and an electronic device to be monitored whenperforming maintenance of the electronic device.

[0015] Also, an object of the present invention is to provide anelectronic device monitoring method, an electronic device, a computerand its program capable of integrally performing monitoring andmaintenance of the above electronic device.

[0016] Also, an object of the present invention is to provide anelectronic device monitoring method, an electronic device, a computerand its program capable of saving a trouble of the user at the time ofsetting to the electronic device an IP address as a transmissiondestination of a Trap.

[0017] To attain the above objects, an electronic device maintenancemethod of the first invention is an electronic device maintenance methodfor performing maintenance of an electronic device by a computer via anetwork, comprising a first step that the computer obtains remotemaintenance management data indicating a communication protocol used ina communication relating to maintenance of the electronic device fromthe electronic device via the network; and a second step that thecomputer performs processing relating to maintenance of the electronicdevice by performing a communication with the electronic device by usingthe communication protocol indicated by the remote maintenancemanagement data obtained in the first step.

[0018] Preferably, an electronic device maintenance method of the firstinvention further includes a third step that, when connection by theelectronic device to the network is recognized, the computer obtainsidentification data of the recognized electronic device on the network;and in the second step, the computer performs the communication with theelectronic device by further using the identification data obtained inthe third step.

[0019] Preferably, in an electronic device maintenance method of thefirst invention, in the first step, the computer obtains from theelectronic device the remote maintenance management data indicatingcorrespondence between a kind of one or a plurality of functionsrelating to the maintenance and the communication protocol used incommunication relating to the function; and in the second step, thecomputer performs communication relating to the specified kind offunction by using the communication protocol corresponding to thespecified kind of function with the electronic device based on theremote maintenance management data.

[0020] Preferably, an electronic device maintenance method of the firstinvention further includes a sixth step that the computer automaticallywrites to the electronic device identification data for identifying thecomputer on a network as transmission destination data; and a seventhstep that the electronic device transmits an interruption signal to thecomputer by using the transmission destination data written in the sixthstep when the electronic device becomes a predetermined condition.

[0021] A computer of the second invention is a computer for performingmaintenance of an electronic device via a network, comprising aninterface for performing a communication with the electronic device viathe network; a memory means for storing remote maintenance managementdata indicating a communication protocol used in a communicationrelating to maintenance of the electronic device obtained from theelectronic device via the interface; and a control means for performingprocessing relating to maintenance of the electronic device byperforming a communication with the electronic device via the interfaceby using the communication protocol indicated by the remote maintenancemanagement data stored in the memory means.

[0022] An electronic device of the third invention is an electronicdevice subjected to maintenance by a computer via a network, comprisingan interface for performing a communication with the computer via thenetwork; a memory means for storing remote maintenance management dataindicating a communication protocol used in a communication relating tomaintenance by the computer; and a control means for transmitting theremote maintenance management data to the computer via the interface andperforms a communication relating to the maintenance with the computerby using the communication protocol indicated by the remote maintenancemanagement data in accordance with a request from the computer.

[0023] A program of the fourth program is a program executed by acomputer for performing maintenance of an electronic device via anetwork, comprising a first step for receiving remote maintenancemanagement data indicating a communication protocol used in acommunication relating to maintenance of the electronic device from theelectronic device via the network; a second step for storing the remotemaintenance management data received in the first step in a memory meansprovided to the computer; and a third step for processing relating tomaintenance of the electronic device by performing a communication withthe electronic device via the network by using the communicationprotocol indicated by the remote maintenance management data stored inthe memory means.

[0024] A program of the fifth invention is a program executed in anelectronic device subjected to maintenance by a computer via a network,comprising a first step for transmitting to the computer via the networkremote maintenance management data indicating a communication protocolused in a communication relating to maintenance of the electronic devicewith the computer; and a second step for performing communicationrelating to the maintenance with the computer by using the communicationprotocol indicated by the remote maintenance management data.

BRIEF DESCRIPTION OF DRAWINGS

[0025]FIG. 1 is a view of the overall configuration of a communicationsystem according to a first embodiment of the present invention.

[0026]FIG. 2 is a view of the configuration of a computer and a deviceto be monitored shown in FIG. 1.

[0027]FIG. 3 is a view for explaining SNMP communication processing.

[0028]FIG. 4 is a view for explaining remote maintenance management datastored in a private MIB shown in FIG. 3.

[0029]FIG. 5 is a view for explaining kinds of functions in the remotemaintenance management data shown in FIG. 4.

[0030]FIG. 6 is a view for explaining service levels in the remotemaintenance management data shown in FIG. 4.

[0031]FIG. 7 is a view for explaining an example of the remotemaintenance management data shown in FIG. 4.

[0032]FIG. 8 is a flowchart for explaining an operation example of thecommunication system shown in FIG. 1.

[0033]FIG. 9 is a view for explaining a process that a user of acomputer selects a maintenance function on a screen in FIG. 8.

[0034]FIG. 10 is a view for explaining a display format of status dataon the screen of the computer in FIG. 8.

[0035]FIG. 11 is a view for explaining a display on the screen of thecomputer at the time of downloading software in FIG. 8.

[0036]FIG. 12 is a view of the overall configuration of a communicationsystem of a second embodiment of the present invention.

[0037]FIG. 13 is a view of the configuration of the computer andelectronic device shown in FIG. 12.

[0038]FIG. 14 is a view for explaining the SNMP communicationprocessing.

[0039]FIG. 15 is a view for explaining data to be stored in a ROM/RAMand an HDD of the electronic device shown in FIG. 13.

[0040]FIG. 16 is a view for explaining a Trap transmission destinationtable shown in FIG. 15.

[0041]FIG. 17 is a view for explaining meanings of values of statuses ofthe Trap transmission destination table shown in FIG. 16.

[0042]FIG. 18 is a flowchart for explaining processing at the time ofstarting up, rebooting or initializing the electronic device shown inFIG. 12.

[0043]FIGS. 19A to 19F are views for explaining processing conditions ofthe electronic device in response to requests by the computer.

[0044]FIG. 20 is a view for explaining the case where an automaticsetting variable shown in FIG. 15 is off.

[0045]FIG. 21 is a view for explaining the case of setting the Traptransmission destination table on the electronic device side.

[0046]FIGS. 22A and 22B are views for explaining the case where theautomatic setting variable shown in FIG. 15 shifts from off to on.

[0047]FIGS. 23A and 23B are views for explaining the case where theautomatic setting variable shown in FIG. 15 shifts from on to off.

[0048]FIG. 24 is a flowchart for explaining an operation example of thecommunication system shown in FIG. 12 when an SNMP manager sets to theelectronic device an IP address of the computer as a Trap transmissionaddress in a state wherein a Trap transmission address of an entry onthe first line in the Trap transmission destination table is “0. 0. 0.0” and a status thereof is “valid”.

[0049]FIG. 25 is a flowchart for explaining an operation example of thecommunication system shown in FIG. 12 at the time an SNMP manager ofanother computer sets to the electronic device the IP address of thecomputer as a Trap transmission address in the state wherein a Traptransmission address of an entry on the first line of the Traptransmission destination table is not “0. 0. 0. 0” (a state wherein anIP address of the computer is already set).

[0050]FIGS. 26A, 26B and 26C are views for explaining conditions of theTrap transmission destination table in the operation example shown inFIG. 25.

[0051]FIG. 27 is a flowchart for explaining the case where an addresschange request from the SNMP manager of the computer is generated almostsimultaneously with an address change request of an address generatedfrom an SNMP manager of another computer to an entry on the first lineof the Trap transmission destination table.

[0052]FIG. 28 is a flowchart for explaining an operation example of thecase where an adding request of an entry on the second line in the Traptransmission destination table is generated from another computer almostsimultaneously with that from the computer.

[0053]FIG. 29 is a flowchart for explaining the operation example of thecase where abnormality or an event arises in the electronic device shownin FIG. 12, so a necessity arises that the electronic device transmits aTrap to the computer.

BEST MODE FOR CARRYING OUT THE INVENTION

[0054] Below, a communication system according to embodiments of thepresent invention will be explained.

[0055] First Embodiment

[0056]FIG. 1 is a view of the overall configuration of a communicationsystem 1 according to the present embodiment.

[0057] As shown in FIG. 1, in the communication system 1, for example, acomputer 2 as a device to be monitored and an electronic device 3 as adevice to be monitored are connected in a predetermined area 6 via anetwork, such as a LAN (Local Area Network) 5 and the Internet.

[0058] Here, the computer 2 corresponds to a computer of the presentinvention and the electronic device 3 corresponds to an electronicdevice of the present invention.

[0059] The computer 2 and the electronic device 3 have a function ofperforming processing relating to the SNMP as a connectionless typenetwork management protocol operating on a UDP transport layer of theTCP/IP.

[0060] In the communication system 1 shown in FIG. 1, the computer 2 andthe electronic device 3 perform an SNMP communication, define acommunication protocol, etc. used for realizing a remote maintenance(monitoring) function in respective MIBs of the computer 2 and theelectronic device 3, and perform remote maintenance by using thedefinition.

[0061] Note that in the present specification, the maintenance alsoincludes monitoring.

[0062] As a result, a load at the time the user performs remotemaintenance of the electronic device 3 by using the computer 2 isreduced.

[0063] [Computer 2]

[0064]FIG. 2 us a view of the configuration of the computer 2 and theelectronic device 3 shown in FIG. 1.

[0065] As shown in FIG. 2, in the computer 2, for example, a ROM/RAM 11,an HDD 12, a KB_1/F 13, a DP_IF 15, a LAN_I/F 17 and a CPU 18 areconnected via an internal bus 19.

[0066] Here, the LAN_I/F 17 corresponds to an interface means of thecomputer of the present invention, the ROM/RAM 11 and the HDD 12correspond to a memory means of the computer of the present invention,and the CPU 18 corresponds to a control means of the computer of thepresent invention.

[0067] The ROM/RAM 11 stores a program for realizing a variety offunctions provided by the computer 2 including an SNMP processingfunction.

[0068] The HDD 12 stores various data used in processing in the computer2.

[0069] Also, as will be explained later on, a remote maintenancemanagement table received (inputted) from the electronic device 3 viathe LAN 5 is written in the ROM/RAM 11 or/and the HDD 12.

[0070] The KB_I/F 13 is connected to an operation means (a specifyingmeans of the present invention), such as a keyboard KB14 and a mouse.

[0071] The DP_IF 15 is connected to a display DP16 (a display means ofthe present invention), etc.

[0072] The LAN_I/F 17 is connected to the LAN 5.

[0073] The CPU 18 realizes a variety of functions, such as an SNMPprocessing function and a remote maintenance function, for example,based on a program read from the ROM/RAM 11.

[0074] [Electronic Device 3]

[0075] As shown in FIG. 2, in the electronic device 3, for example, aROM/RAM 21, an HDD 22, an I/O 23, a LAN_I/F 26 and a CPU 27 areconnected via an internal bus 28.

[0076] Here, the LAN_I/F 26 corresponds to an interface means of theelectronic device of the present invention, the CPU 27 corresponds to acontrol means of the electronic device of the present invention, and theROM/RAM 21 and the HDD 22 correspond to a memory means of the electronicdevice of the present invention.

[0077] In the present embodiment, the electronic device 3 is for examplea television device, an audio device, lighting and other electronicdevices.

[0078] The ROM/RAM 21 stores a program for realizing a variety offunctions provided by the electronic device 3 including an SNMPprocessing function.

[0079] The HDD 22 stores various data used by processing in theelectronic device 3.

[0080] Also, the ROM/RAM 21 and/or the HDD 22 store a remote maintenancemanagement table used in remote maintenance by the computer 2.

[0081] The remote maintenance management table will be explained indetail later on.

[0082] The I/O 23 is connected to a control panel 24 and an electriccircuit/mechanic unit 25, etc.

[0083] The LAN_I/F 26 is connected to the LAN 5.

[0084] The CPU 27 realizes a variety of functions, such as an SNMPprocessing function, for example, based on a program read from theROM/RAM 21.

[0085] [SNMP Communication Processing]

[0086] Next, SNMP communication processing performed between thecomputer 2 and the electronic device 3 shown in FIG. 1 will beexplained.

[0087]FIG. 3 is a view for explaining the SNMP communication processing.

[0088]FIG. 3 is a view for explaining the SNMP communication processingperformed between the computer 2 and the electronic device 3.

[0089] The CPU 18 of the computer 2 executes a program (a program of thefourth invention) read from the ROM/RAM 11 or the HDD 12 and realizes anSNMP manager 80.

[0090] Also, the CPU 27 of the electronic device 3 executes a program (aprogram of the fifth invention) read from the ROM/RAM 21 or the HDD 22and realizes an SNMP agent 81.

[0091] Also, the ROM/RAM 21 or the HDD 22 of the electronic device 3stores, for example, data of a private MIB (Management Information Base)82 and a MIB II 83.

[0092] The private MIB 82 is an MIB peculiar to a vender originallydefined for the vender of the electronic device 3 for managing productsof the own company.

[0093] In the present embodiment, the remote maintenance management data85 explained above is stored in the private MIB 82.

[0094] The MIB II 83 is an MIB wherein management information of aTCP/IP level is defined.

[0095] The SNMP agent 81 obtains information to be managed and notifiesthe information to the SNMP manager 80 by using a network managementprotocol of the SNMP. Information needing to be managed is stored in theprivate MIB 82 and/or MIB II 83 of the electronic device 3.

[0096] Also, in the present embodiment, as shown in FIG. 3, also the MIB84 of the computer 2 stores the remote maintenance management data 85.

[0097] Data of the MIB 84 is stored in the ROM/RAM 11 and/or the HDD 12of the computer 2 shown in FIG. 2.

[0098] The SNMP agent 81 transmits information in the private MIB 82and/or the MIB II 83 to the SNMP manager 80 based on a request from theSNMP manager 80. Note that when an irregular event occurs, such that theelectronic device 3 reboots, the SNMP agent 81 transmits a Trap to theSNMP manager 80.

[0099] A request of obtaining or setting a value of an object to bemanaged is given from the SNMP manager 80 to the SNMP agent 81 and theSNMP agent 81 responds to the request. Also, the SNMP agent 81 notifiesthe irregularity or an event arisen in the electronic device 3 to theSNMP manager 80. To realize the functions, five operations below areregulated in the SNMP.

[0100] GET REQUEST: reading data stored in an MIB variable specifiedfrom the private MIB 82 and/or the MIB II 83

[0101] GETNEXT REQUEST: reading next data of a specified MIB variable byfollowing a procedure of the private MIB 82 and/or the MIB II 83

[0102] SET REQUEST: setting an MIB variable to specified data

[0103] GET RESPONSE: a response from the SNMP agent 81 to a request

[0104] Trap: notifying arising of abnormality and an event from the SNMPagent 81 to the SNMP manager 80

[0105] The private MIB 82 and the MIB II 83 store definition of anobject (an amount or a field) provided by the SNMP agent 81 to the SNMPmanager 80. The object defined by the private MIB 82 and the MIB II 83is arranged in unit of a group and relates to respective layers or aprotocol in a protocol stack of a certain group, while other group as awhole relates to a system.

[0106] The private MIB 82 and the MIB II 83 is added an objectidentifier to uniquely identify any management object and the objectidentifier has a tree structure starting from a root element.

[0107] In the present embodiment, when the electronic device 3 isconnected to the LAN 5 shown in FIG. 1, the SNMP manager 80 of thecomputer 2 shown in FIG. 3 automatically recognizes (discovery) theelectronic device 3 and automatically registers an IP address and a hostname of the electronic device 3, for example, to the MIB 84 by the “Plugand Play”.

[0108] [Remote Maintenance Management Data 85]

[0109] Below, the remote maintenance management data 85 stored in theprivate MIB 82 of the electronic device 3 and the MIB 84 in the computer2 explained above will be explained in detail. FIG. 4 is a view of theconfiguration of the remote maintenance management data 85.

[0110] As shown in FIG. 4, the remote maintenance management data 85 hasone or a plurality of entries each comprising an Index number“proV1RemoteMainteIdx” which is data indicating an index number forspecifying an entry, “proV1RemoteMainteFunction” (maintenance functionspecification data of the present invention) which is data indicating akind of a function of remote maintenance, “proV1RemoteMainteProtoType”(communication protocol specification data of the present invention)which is data indicating a kind of a communication protocol used in acommunication between the computer 2 and the electronic device 3 at thetime of performing remote maintenance by using the function,“proV1RemoteMainteProtoVer” which is data indicating a version of thecommunication protocol, “proV1RemoteMaintePath” (path specificationdata” which is data indicating an access path to a memory region of theROM/RAM 21 or the HDD 22 storing data or a program relating to theremote maintenance, and “proV1RemoteMainteSvcLevel” (use authority dataof the present invention) which is data indicating a service level forspecifying persons to be permitted to use or disclosed the function.

[0111] The data “proV1RemoteMainteFunction” indicating a kind of afunction of the remote maintenance is a 32-bit integer type.

[0112] The SNMP manager 80 of the computer 2 refers to the data“proV1RemoteMainteFunction” in accordance with an instruction(specification) inputted for example from the keyboard 14, reads aprogram of a specified function from the ROM/RAM 11 or the HDD12 andexecutes.

[0113] The data “proV1RemoteMainteFunction” indicates a kind of afunction to which, for example, each of values “01”, “02”, “11”, “12”,“21”, “31”, “41”, “42” “43”, “51”, “61”, “62”, “71”, “72” and “81”corresponds as shown in FIG. 5.

[0114] Here, values “01” and “02” indicate a function relating tomonitoring. The value “01” indicates a function for monitoring apredetermined item of the MIB II 83 of the electronic device 3 shown inFIG. 3, and the value “02” indicates a function for monitoring apredetermined item of the private MIB 82 of the electronic device 3shown in FIG. 3.

[0115] Also, values “11”, “12”, “21”, “31”, “41”, “42”, “43”, “51”,“61”, “62”, “71”, “72” and “81” indicate functions relating to themaintenance.

[0116] For example, the value “11” indicates a function that the SNMP 81notifies an error or a warning to the SNMP manager 80 by using ane-mail.

[0117] The value “12” indicates a function that the SNMP manager 80operates the electronic device 3 by using an e-mail.

[0118] The value “21” indicates a function that the SNMP manager 80refers to a status indicating a condition of the electronic device 3stored in the private MIB 82 and/or the MIB II 83 and/or other databaseor a file.

[0119] The value “31” indicates a function that the SNMP manager 80collects record data (log) of processing in the electronic device 3stored in the private MIB 82 and/or the MIB II 83 and/or other data baseor a file.

[0120] The value “41” indicates a function that the SNMP manager 80refers to and changes a predetermined set value and compositioninformation of the electronic device 3.

[0121] The value “42” indicates a function that the SNMP manager 80downloads a predetermined set value of the electronic device 3 to theelectronic device 3.

[0122] The value “43” indicates a function that the SNMP manager 80uploads a predetermined set value of the electronic device 3.

[0123] The value “51” indicates a function that the SNMP manager 80executes diagnosis processing of the electronic device 3.

[0124] The value “61” indicates a function that the SNMP manager 80downloads for example software used by processing in the SNMP agent 81to the electronic device 3.

[0125] The value “62” indicates a function that the SNMP manager 80uploads a predetermined software from the electronic device 3.

[0126] The value “71” indicates a function that the SNMP manager 80resets or reboots the electronic device 3.

[0127] The value “72” indicates a function that the SNMP manager 80switches various modes set in the electronic device 3.

[0128] Also, the value “81” indicates a function that for example theSNMP manager 80 controls predetermined processing performed in theelectronic device 3.

[0129] The data “proV1RemoteMainteProtoType” is a number indicating akind of a communication protocol used in a communication between thecomputer 2 and the electronic device 3 at the time of performing remotemaintenance by using a corresponding function as explained above. A portnumber is used as the number.

[0130] The SNMP manager 80 of the computer 2 refers to the data“proV1RemoteMainteProtoType” corresponding to a specified function inresponse to an instruction (specification) inputted for example from thekeyboard 14, uses a communication protocol specified thereby andperforms communication with the electronic device 3.

[0131] The data “proV1RemoteMainteProtoType” indicates, for example, avalue “80” when the HTTP is used, a value “20” when the FTP is used, avalue “23” when the TELENET is used, a value “25” when the SMTP (SimpleMail Transfer Protocol) is used, a value “110” when the POP3 is used anda value “161” when the SNMP is used as a communication protocol.

[0132] The data “proV1RemoteMainteProtoVer” indicates a version of acorresponding communication protocol and has a value indicating theversion as explained above.

[0133] The data “proV1RemoteMaintePath” indicates a path to access firstat the time of accessing to the electronic device 3 by using an accesspath to a memory region of the ROM/RAM 21 or the HDD 22 storing data ora program used in a corresponding function, that is the HTTP (WebBrowser) or the FTP (FTP client) as explained above.

[0134] For example, when an IP address of the electronic device 3 is“192. 168. 10. 101” and a path in the electronic device 3 to access atthe time of executing a setup change function is “/setup”, the data“proV1RemoteMaintePath” indicates “/setup”.

[0135] The SNMP manager 80 of a specific vender operates to access forexample to an URL “http://192. 168. 10. 101/setup” by a browser bycombining information of the IP address and the path.

[0136] The SNMP manager 80 refers to “proV1RemoteMaintePath”corresponding to a specified function in accordance with an instruction(specification) inputted for example from the keyboard 14 and, byfollowing a path specified thereby, makes an access to a memory regionof the electronic device 3 during processing relating to the specifiedfunction.

[0137] The data “proV1RemoteMainteSvcLevel” indicates a number of aservice level for specifying persons to whom the corresponding functionis permitted to be used or disclosed, that is, a service level of aremote maintenance function as explained above.

[0138] The SNMP manager 80 refers to “proV1RemoteMainteSvcLevel”corresponding to a specified function in accordance with an instruction(specification) inputted for example from the keyboard 14 and, byfollowing a service level specified thereby, judges persons to whom thecorresponding function is permitted to be used or disclosed.

[0139] Specifically, the data “proV1RemoteMainteSvcLevel” indicatesbeing used only by a production division of the electronic device 3 whenat a level “0” as shown in FIG. 6. Also, when at a level “1”, itindicates being able to be used by the above production division andservice footholds (sales) in the vender. Also, at a level “2”, itindicates being able to be used by the above service footholds (sales)and service footholds (agents) outside the vender. When at a level “3”,it indicates being able to be used by the above production division, theabove service footholds (sales), the service footholds (agents) outsidethe vender and a manager on the customer side. When at a level “4”, itindicates being able to be used by the above production division, theabove service footholds (sales), the service footholds (agents) outsidethe vender, a manager on the customer side and general users.

[0140] Below, an example of the remote maintenance management data 85shown in FIG. 4 will be explained.

[0141]FIG. 7 is a view for explaining an example of the remotemaintenance management data 85 shown in FIG. 4.

[0142] As shown in FIG. 7, in this example, the remote maintenancemanagement data 85 comprises seven entries, each of which is added anIndex number from “1” to “7”.

[0143] An entry having an Index number “1” is set “01” indicating amonitoring function of the MIB II 83 as “proV1RemoteMainteFunction”,“161” indicating the SNMP as “proV1RemoteMainteProtoType”, “100” as“proV1RemoteMainteProtoVer”, and a level “3” as“proV1RemoteMainteSvcLevel”.

[0144] Also, an entry having an Index number “2” is set “02” indicatinga monitoring function of the private MIB 82 as“proV1RemoteMainteFunction”, “161” indicating the SNMP as“proV1RemoteMainteProtoType”, “100” as “proV1RemoteMainteProtoVer” and alevel “3” as “proV1RemoteMainteSvcLevel”.

[0145] Also, an entry having an Index number “3” is set “21” indicatinga function of referring to a status of the electronic device 3 as“proV1RemoteMainteFunction”, “80” indicating the HTTP as“proV1RemoteMainteProtoType”, “110” as “proV1RemoteMainteProtoVer”,“/service/status” as “proV1RemoteMaintePath” and a level “1” as“proV1RemoteMainteSvcLevel”.

[0146] Also, an entry having an Index number “4” is set “31” indicatinga function of collecting record data (log) of the electronic device 3 as“proV1RemoteMainteFunction”, “20” indicating the FTP as“proV1RemoteMainteProtoType”, “/var/log” as “proV1RemoteMaintePath” anda level “1” as “proV1RemoteMainteSvcLevel”.

[0147] Also, an entry having an Index number “5” is set “41” indicatinga function of referring to or changing a set value or compositioninformation of the electronic device 3 as “proV1RemoteMainteFunction”,“80” indicating the HTTP as “proV1RemoteMainteProtoType”, “110” as“proV1RemoteMainteProtoVer”, “/setup” as “proV1RemoteMaintePath” and alevel “3” as “proV1RemoteMainteSvcLevel”.

[0148] Also, an entry having an Index number “6” is set “51” indicatinga function of executing diagnosis processing of the electronic device 3as “proV1RemoteMainteFunction”, “80” indicating the HTTP as“proV1RemoteMainteProtoType”, “110” as “proV1RemoteMainteProtoVer”,“/service/diag” as “proV1RemoteMaintePath” and a level “1” as“proV1RemoteMainteSvcLevel”.

[0149] Also, an entry having an Index number “7” is set “61” indicatinga function of downloading software to the electronic device 3 as“proV1RemoteMainteFunction”, “20” indicating the FTP as“proV1RemoteMainteProtoType”, “/temp/firmware” as“proV1RemoteMaintePath” and a level “1” as “proV1RemoteMainteSvcLevel”.

[0150] Below, an operation example of the communication system 1 shownin FIG. 1 will be explained.

[0151]FIG. 8 is a flowchart for explaining the operation example.

[0152] Step ST1:

[0153] When the electronic device 3 is connected to the LAN 5 shown inFIG. 1, the SNMP manager 80 shown in FIG. 3 realized as a result thatthe CPU 18 of the computer 2 executes a predetermined program obtains anIP address or a host name of the electronic device 3 by “discovery”(automatic recognition) and stores the same for example in the MIB 84 ofthe computer 2.

[0154] Step ST2:

[0155] The SNMP manager 80 transmits a request “GET REQUEST” regulatedby the SNMP communication to the SNMP agent 81 of the electronic device3 from the LAN_I/F 17 shown in FIG. 2 via the LAN 5.

[0156] Due to this, the SNMP agent 81 shown in FIG. 3 realized as aresult that the CPU 27 of the electronic device 3 executes apredetermined program reads the remote maintenance management data 85stored in the private MIB 82 and transmits the remote maintenancemanagement data 85 from the LAN_I/F 26 shown in FIG. 2 to the computer 2via the LAN 5.

[0157] The computer 2 stores the remote maintenance management data 85received from the electronic device 3 in the MIB 84 shown in FIG. 3.

[0158] Step ST3:

[0159] The SNMP manager 80 executes the GUI (Graphical User Interface)and displays on the display 16 shown in FIG. 2, for example, a screen100 of a maintenance menu shown in FIG. 9 in accordance with the remotemaintenance management data 85 stored in the MIB 84 in the step ST2.

[0160] Step ST4:

[0161] After a user of the computer 2 specifies an icon corresponding tothe electronic device 3 for example on the screen 100 shown in FIG. 9,the user specifies an item corresponding to the maintenance function andsuccessively specifies an item corresponding to status reference.

[0162] Due to this, the SNMP manager 80 reads a program corresponding tothe status reference function from the ROM/RAM 11 or the HDD 12 shown inFIG. 2 and executes the same, performs communication with the SNMP agent81 via the LAN 5, receives status data (status data of the presentinvention) of the electronic device 3 and displays for example a screen101 shown in FIG. 10 in accordance therewith on the display 16.

[0163] At this time, communication is performed between the SNMP manager80 and the SNMP agent 81 by using the HTTP as a communication protocolbased on information, such as a kind of a protocol in the remotemaintenance management data 85 shown in FIG. 7.

[0164] Step ST5:

[0165] The user of the computer 2 successively specifies an itemcorresponding to log collection for example on the screen 100 shown inFIG. 9.

[0166] Due to this, the SNMP manager 80 reads a program corresponding toa log collective function from the ROM/RAM 11 or the HDD 12 shown inFIG. 2 and executes the same, performs communication with the SNMP agent81 via the LAN 5, receives record (log) data from the electronic device3 and displays a screen in accordance therewith on the display 16.

[0167] At this time, communication between the SNMP manager 80 and theSNMP agent 81 by using the FTP as a communication protocol is performedbased on information, such as a kind of a protocol in the remotemaintenance management data 85 shown in FIG. 7.

[0168] Step ST6:

[0169] The user of the computer 2 successively specifies an itemcorresponding to software download for example on the screen 100 shownin FIG. 9.

[0170] Due to this, the SNMP manager 80 displays a screen 102 shown inFIG. 11 on the display 16, reads predetermined software (program) fromthe ROM/RAM 11 or the HDD 12 shown in FIG. 2 in response to an operationon the screen 102 by the user, performs communication with the SNMPagent 81 via the LAN 5 and downloads the read software to the electronicdevice 3.

[0171] At this time, communication is performed between the SNMP manager80 and the SNMP agent 81 by using the FTP as a communication protocolbased on information, such as a kind of a protocol in the remotemaintenance management data 85 shown in FIG. 7.

[0172] Step ST7:

[0173] The SNMP agent 81 of the electronic device 3 executes thesoftware downloaded in the step ST6 after performing initializationprocessing.

[0174] Step ST8:

[0175] The SNMP manager 80 executes a program for example relating to avariety of functions shown in FIG. 5, monitors and controls an operation(processing) of the electronic device 3.

[0176] As explained above, according to the communication system 1, thecomputer 2 performs a communication with the electronic device 3 byusing a communication protocol corresponding to a kind of a function tobe executed (specified) based on information, such as a kind of aprotocol indicated by the remote maintenance management data 85 receivedfrom the electronic device 3.

[0177] As a result, it becomes unnecessary for the administrator of thecomputer 2 to set the communication protocol used in the communicationwith respective electronic devices 3 and the load is reduced.

[0178] Also, the electronic device 3 is capable of performingcommunication with the computer 2 by using a communication protocolsuitable to itself.

[0179] Also, according to the communication system 1, by holding theabove remote maintenance management data 85 in the electronic device 3and the computer 2 and performing monitoring and maintenance of theelectronic device 3 based on the remote maintenance management data 85by the computer 2, monitoring and maintenance of the electronic device 3by the computer 2 can be integrally performed and a load on the user ofthe computer 2 can be reduced.

[0180] Namely, it becomes unnecessary for the user of the computer 2 toinquire an IP address, communication protocol of the electronic device 3and an access path to the memory region of the electronic device 3 priorto the maintenance of the electronic device 3.

[0181] Second Embodiment

[0182]FIG. 12 is a view of the overall configuration of a communicationsystem 1 a of a second embodiment of the present invention.

[0183] As shown in FIG. 12, in the communication system 1 a, for examplecomputers 2 a and 2 b and an electronic device 3 a are connected via aLAN (Local Area Network) 5 in an area 6 a.

[0184] Also, the computers 2 a and 2 b and the electronic device 3 aperforms communication via the LAN 5 in the area 6 a.

[0185] Here, the computers 2 a and 2 b correspond to the computer of thepresent invention and the electronic device 3 a corresponds to theelectronic device of the present invention.

[0186] The computers 2 a and 2 b and the electronic device 3 a have afunction of performing processing relating to the SNMP as aconnectionless type network management protocol operating on a UDPtransport layer of the TCP/IP.

[0187] The computers 2 a and 2 b have for example all the configurationof the computer 2 of the first embodiment.

[0188] Also, the electronic device 3 a has for example all theconfiguration of the electronic device 3 of the first embodiment.

[0189] In the communication system 1 a shown in FIG. 12, the computers 2a and 2 b and the electronic device 3 a perform SNMP communication andwhen abnormality or an event occurs in the electronic device 3 a, theelectronic device 3 a transmits a Trap (an interruption signal of thepresent invention) to the computers 2 a and 2 b and notifies the fact.

[0190] In the electronic device 3 a, a Trap transmission destinationtable for managing transmission addresses of the Trap is prepared.

[0191] In the present embodiment, the computers 2 a and 2 bautomatically write own IP addresses to the Trap transmissiondestination table of the electronic device 3 a.

[0192] [Computers 2 a and 2 b]

[0193]FIG. 13 is a view of the configuration of the computer 2 a and theelectronic device 3 a shown in FIG. 12.

[0194] Note that the computer 2 b has basically the same configurationas that of the computer 2 a.

[0195] As shown in FIG. 13, in the computer 2 a, for example a ROM/RAM11 a, an HDD 12 a, a KB_I/F 13 a, a DP_I/F 15 a, a LAN_I/F 17 a and aCPU 18 a are connected via an internal bus 19 a.

[0196] Here, the LAN_I/F 17 a corresponds to an interface means of thecomputer of the present invention and the CPU 18 a corresponds to acontrol means of the computer of the present invention.

[0197] The ROM/RAM 11 a stores a program for realizing a variety offunctions provided by the computer 2 a including the SNMP processingfunction.

[0198] The HDD 12 a stores various data used by processing in thecomputer 2 a.

[0199] The KB_I/F 13 a is connected an operation means, such as akeyboard KB 14 a and a mouse.

[0200] The DP_I/F 15 a is connected to a display DP 16 a.

[0201] The LAN_I/F 17 a is connected to the LAN 5.

[0202] The CPU 18 a realizes a variety of functions, such as the SNMPprocessing function, for example, based on a program read from theROM/RAM 11 a.

[0203] [Electronic Device 3 a]

[0204] As shown in FIG. 13, in the electronic device 3 a, for example, aROM/RAM 21 a, an HDD 22 a, an I/O 23 a, a LAN_I/F 26 a and a CPU 27 aare connected via an internal bus 28 a.

[0205] Here, the LAN_I/F 26 a corresponds to the interface means of theelectronic device of the present invention, the CPU 27 a corresponds tothe control means of the electronic device of the present invention andthe ROM/RAM 21 a and the HDD 22 a correspond to the memory means of theelectronic device of the present invention.

[0206] In the present embodiment, the electronic device 3 a is forexample a television device, an audio device, lighting and otherelectronic devices.

[0207] In the ROM/RAM 21 a, a program for realizing a variety offunctions provided by the electronic device 3 a including the SNMPprocessing function is stored.

[0208] In the HDD 22 a, various data used by processing in theelectronic device 3 a is stored.

[0209] The I/O 23 a is connected to a control panel 24 a and an electriccircuit/mechanic unit 25 a, etc.

[0210] The LAN_I/F 26 a is connected to the LAN 5.

[0211] The CPU 27 a realizes a variety of functions, such as the SNMPprocessing function, based on a program read from the ROM/RAM 21 a.

[0212] [SNMP Communication Processing]

[0213] Next, the SNMP communication processing performed between thecomputer 2 a and the electronic device 3 a shown in FIG. 12 will beexplained.

[0214]FIG. 14 is a view for explaining the SNMP communicationprocessing.

[0215]FIG. 14 is a view for explaining the SNMP communication processingperformed between the computers 2 a and 2 b and the electronic device 3a.

[0216] The CPU 18 a of the computer 2 a executes a program (a program ofthe fourth invention) read from the ROM/RAM 11 a or the HDD 12 a torealize the SNMP manager 80 a.

[0217] Also, the CPU 27 a of the electronic device 3 a executes aprogram (a program of the fifth invention) read from the ROM/RAM 11 a orthe HDD 12 a to realize the SNMP agent 81 a.

[0218] Also, the HDD 22 a of the electronic device 3 a stores forexample data of the MIB (Management Information Base) 82 a.

[0219] The SNMP agent 81 a obtains information to be managed andnotifies the information to the SNMP manager 80 a by using a networkmanagement protocol of the SNMP. The information needing to be managedis stored in the MIB 82 a as a database.

[0220] The SNMP agent 81 a transmits information in the MIB 82 a to theSNMP manager 80 a based on a request from the SNMP manager 80 a. Notethat when an irregular event occurs, such that the electronic device 3 areboots, the SNMP agent 81 a transmits a Trap to the SNMP manager 80 a.

[0221] A request for obtaining and setting a value of an object to bemanaged is given from the SNMP manager 80 a to the SNMP agent 81 a, andthe SNMP agent 81 a responds to the request. Also, the SNMP agent 81 anotifies abnormality and an event occurred in the electronic device 3 ato the SNMP manager 80 a. To realize the functions, five operationsbelow are regulated in the SNMP.

[0222] GET REQUEST: reading data stored in an MIB variable specifiedfrom the MIB 82 a

[0223] GETNEXT REQUEST: reading next data of a specified MIB variable byfollowing a procedure of the MIB 82 a

[0224] SET REQUEST: setting an MIB variable to specified data

[0225] GET RESPONSE: a response from the SNMP agent 81 a to a request

[0226] Trap: notifying an occurrence of abnormality and an event fromthe SNMP agent 81 a to the SNMP manager 80 a

[0227] The MIB 82 a stores definition of an object (an amount or afield) provided by the SNMP agent 81 a to the SNMP manager 80 a. Theobject defined by the MIB 82 a is arranged in unit of a group andrelates to respective layers or a protocol in a protocol stack of acertain group, while other group as a whole relates to a system.

[0228] The MIB 82 a is added an object identifier to uniquely identifyany management object and the object identifier has a tree structurestarting from a root element.

[0229] As shown in FIG. 15, in the ROM/RAM 21 a or the HDD 22 a, an IPaddress 41, a Trap transmission destination table 42 (table data of thepresent invention) and an automatic setting variable 43 of theelectronic device 3 a are stored.

[0230] Here, the Trap transmission destination table 42 is stored in theMIB 82 a.

[0231] In the present embodiment, the SNMP agent 81 a of the electronicdevice 3 a and the SNMP managers 80 a of the computers 2 a and 2 b shownin FIG. 14 negotiate via the LAN 5 and automatically set (the Plug andPlay) the Trap transmission destination table stored in the MIB 82 a.

[0232] [Trap Transmission Destination Table 42]

[0233]FIG. 16 is a view for explaining the Trap transmission destinationtable 42.

[0234] As shown in FIG. 16, the Trap transmission destination table 42is named “proV1TrapDestTable” and composed of a plurality of entries“proV1TrapDestEntry”.

[0235] Each entry “proV1TrapDestEntry” is composed for example of 32bits of an integer type index number “proV1TrapDestIdx”, a Traptransmission destination address “proV1TrapDestAddress” in which an IPaddress is stored (transmission destination data of the presentinvention), and a status of the entry “proV1TrapDestStatus” (status dataof the present invention).

[0236]FIG. 17 is a view for explaining a value of the status of theentry “proV1TrapDestStatus” shown in FIG. 16 and meaning thereof.

[0237] As shown in FIG. 17, when the status “proV1TrapDestStatus” is“1”, it indicates “valid”, when “2”, it indicates a state of an addingrequest of a line entry from the SNMP manager 80 a to the SNMP agent 81a, when “3”, it indicates ending of an operation of generating a lineentry from the SNMP agent 81 a to the SNMP manager 80 a, when “4”, itindicates invalidity of the entry, and when “5”, it indicates that an IPaddress 41 is set being fixed.

[0238] Below, processing at the time of starting up, rebooting orinitializing the electronic device 3 a will be explained.

[0239]FIG. 18 is a flowchart for explaining the processing.

[0240] Step ST11:

[0241] The SNMP agent 81 a shown in FIG. 14 judges whether theelectronic device 3 a is a device compatible to automatic setting ornot, and proceeds to processing of the step ST13 when judged to becompatible to automatic setting, while not, proceeds to processing ofthe step ST12.

[0242] Step ST12:

[0243] The SNMP agent 81 a sets the status of the all entries“EntryStatus” of the Trap transmission destination table 42 shown inFIG. 16 to be fixed.

[0244] Step ST13:

[0245] The SNMP agent 81 a judges whether the automatic setting variable43 shown in FIG. 15 is at “ON” (indicating automatic setting) or not,and proceeds to processing of the step ST15, while not, proceeds toprocessing of the step ST14.

[0246] Step ST14:

[0247] The SNMP agent 81 a sets the status of the all entries“EntryStatus” of the Trap transmission destination table 42 shown inFIG. 16 to be fixed.

[0248] Step ST15:

[0249] Thereby, the SNMP agent 81 a corresponds to automatic setting ofthe Trap transmission destination table 42.

[0250] Step ST16:

[0251] The SNMP agent 81 a judges whether the IP address 41 of theelectronic device 3 a has changed from the previous time of beingstarted up, rebooted or initialized, and proceeds to processing of thestep ST18 when judged to be changed, while not, proceeds to processingof the step ST17.

[0252] Step ST17:

[0253] The SNMP agent 81 a does not initialize the Trap transmissiondestination table 42 and uses what set at the previous starting up as itis.

[0254] Step ST18:

[0255] The SNMP agent 81 a initializes the Trap transmission destinationtable 42.

[0256] Namely, the SNMP agent 81 a sets an entry of the Traptransmission destination table 42 to a first line and sets Index=1, aTrap transmission destination address=0. 0. 0. 0 (initial state), and an“EntryStatus”=1 (valid).

[0257] Step ST19:

[0258] As will be explained later on, continued from the step ST18, theSNMP manager 80 a shown in FIG. 14 performs the automatic setting of theTrap transmission destination table 42.

[0259] Below, processing at the time that the SNMP agent 81 a shown inFIG. 14 receives a request “SetRequest” from the SNMP manager 80 a willbe explained.

[0260]FIG. 19 is a view for explaining the processing.

[0261] As shown in FIG. 19A, before processing, when the SNMP agent 81 areceives a “SetRequest” (proV1TrapDestEntryStatus, n, 1) from the SNMPmanager 80 a in a state that Index=n already exists in the Traptransmission destination table 42 and the “EntryStatus”=1 (valid), anentry of the Index=n in the Trap transmission destination table 42 isleft as it is. Then, the SNMP agent 81 a transmits to the SNMP manager80 a “GetResponse” indicating that normal processing has performed.

[0262] As shown in FIG. 19B, before processing, when the SNMP agent 81 areceives “SetRequest” (proV1TrapDestEntryStatus, n, 1) from the SNMPmanager 80 a in a state that Index=n already exists in the Traptransmission destination table 42 and “EntryStatus”=3 (underCreation),an entry of the Index=n in the Trap transmission destination table 42 isvalidated. Then, the SNMP agent 81 a transmits to the SNMP manager 80 a“GetResponse” indicating that normal processing has performed.

[0263] After the processing, the “EntryStatus” of the entry of theindex=n in the Trap transmission destination table 42 is set from “3” to“1”.

[0264] As shown in FIG. 19C, before processing, when the SNMP agent 81 areceives “SetRequest” (proV1TrapDestEntryStatus, n, 1) from the SNMPmanager 80 a in a state that Index=n already exists in the Traptransmission destination table 42 and the “EntryStatus”=4 (invalid) or 5(fixed), the Trap transmission destination table 42 is not changed.

[0265] After the processing, the Trap transmission destination table 42is not changed.

[0266] As shown in FIG. 19D, before processing, when the SNMP agent 81 areceives from the SNMP manager 80 a “SetReuest”(proV1TrapDestEntryStatus, n, 2) indicating adding of an entry in astate a line of Index=n does not exist in the Trap transmissiondestination table 42, the SNMP agent 81 a adds a new entry (line) havinga Trap transmission address=0, 0, 0, 0 in the Trap transmissiondestination table 42. Then, the SNMP agent 81 a transmits to the SNMPmanager 80 a “GetResponse” indicating that normal processing hasperformed.

[0267] After the processing, the “EntryStatus” of the added entry in theTrap transmission destination table 42 is set to be “3”.

[0268] As shown in FIG. 19E, when the SNMP agent 81 a receives from theSNMP manager 80 a “SetRequest” (proV1TrapDestEntryStatus, n, 2) in astate that Index=n already exists in the Trap transmission destinationtable 42, “GetResponse” indicating an error is transmitted because theentry already exists.

[0269] After the processing, values in the Trap transmission destinationtable 42 are not changed.

[0270] As shown in FIG. 19F, when the SNMP agent 81 a receives from theSNMP manager 80 a “SetRequest” (proV1TrapDestEntryStatus, n, 3),“SetRequest” (proV1TrapDestEntryStatus, n, 4) and “SetRequest”(proV1TrapDestEntryStatus, n, 5) regardless of a state before theprocessing, “GetResponse” indicating an error is transmitted from theSNMP agent 81 a to the SNMP manager 80 a. In this case, values of theTrap transmission destination table 42 are not changed.

[0271] Below, a case where the automatic setting variable 43 shown inFIG. 15 is at “OFF” will be explained.

[0272] In this case, as shown in FIG. 20, a Trap transmissiondestination address of an entry of INDEX=1 in the Trap transmissiondestination table 42 is set to “0. 0. 0. 0” and the status of the entryis set to “5 (fixed)”.

[0273] Below, a case where the Trap transmission destination table 42 isset on the electronic device 3 a side will be explained.

[0274] In this case, for example, as shown in FIG. 21, “XX. XX. XX. XX”as an IP address of the computer 2 a is set as a Trap transmissionaddress of an entry of INDEX=1 in the Trap transmission destinationtable 42, and the status is set to “5 (fixed)”. Also, “YY. YY. YY. YY”as an IP address of the computer 2 b is set as a Trap transmissionaddress of an entry of INDEX=2 in the Trap transmission destinationtable 42, and the status is set to “5 (fixed)”.

[0275] Below, a case where the automatic setting variable 43 is switchedfrom “OFF” to “ON” will be explained.

[0276] For example, as shown in FIG. 22A, when the automatic settingvariable 43 is switched from “OFF” to “ON” at the time the Traptransmission destination table 42 is in the state as explained in FIG.21, as shown in FIG. 22B, the statuses of entries on the first andsecond lines are both rewritten to “1 (valid)”.

[0277] Below, a case where the automatic setting variable 43 is switchedfrom “ON” to “OFF” will be explained.

[0278] For example, as shown in FIG. 23A, when the automatic settingvariable 43 is switched from “ON” to “OFF” at the time the Traptransmission destination table 42 is in the state as explained in FIG.22B, as shown in FIG. 23B, the statuses of the entries on the first andsecond lines are both rewritten to “5 (fixed)”.

[0279] Below, an operation example of the communication system 1 a shownin FIG. 12 will be explained.

[0280] [First Operation Example]

[0281] In this operation example, the case will be explained where in astate that a Trap transmission address of the entry on the first line inthe Trap transmission destination table 42 is “0. 0. 0. 0” and thestatus is “1 (valid)”, the SNMP manager 80 a sets an IP address of thecomputer 2 a as the Trap transmission address to the electronic device 3a.

[0282]FIG. 24 is a flowchart for explaining the operation example.

[0283] Step ST21:

[0284] The SNMP manager 80 a realized by the CPU 18 a of the computer 2a shown in FIG. 13 generates a request “SetRequest”(proV1TrapDestAddress. [1], XX. XX. XX. XX) and transmits the same fromthe LAN_I/F 17 a to the electronic device 3 a via the LAN 5.

[0285] Step ST22:

[0286] The SNMP agent 81 a realized by the CPU 27 a of the electronicdevice 3 a shown in FIG. 13 makes an access to the ROM/RAM 21 a or theHDD 22 a in response to the request received from the SNMP manager 80 avia the LAN_I/F 26 a shown in FIG. 13 in the step ST21 and changes theTrap transmission address of the first entry in the Trap transmissiondestination table 42 shown in FIG. 16 to “XX. XX. XX. XX”.

[0287] Thereby, “XX. XX. XX. XX” as an IP address (identification dataof the computer in the present invention) of the computer 2 a isautomatically set to the first entry in the Trap transmissiondestination table 42.

[0288] Step ST23:

[0289] The SNMP agent 81 a transmits a response “GetResponse” indicatingthat normal processing has completed from the LAN_I/F 26 a to thecomputer 2 a via the LAN 5.

[0290] [Second Operation Example]

[0291] In this operation example, the case will be explained where in astate that a Trap transmission address of the entry on the first line inthe Trap transmission destination table 42 is not “0.0.0.0” (a state theIP address of the computer 2 a is already set), the SNMP manager 80 a ofthe computer 2 b sets an IP address of the computer 2 b as the Traptransmission address to the electronic device 3 a.

[0292]FIG. 25 is a flowchart for explaining the operation example.

[0293] Step ST31:

[0294] The SNMP manager 80 a realized by the CPU 18 a of the computer 2b shown in FIG. 13 generates a request “SetRequest”(proV1TrapDestEntryStatus. [max(index)+1], 2) and transmits the samefrom the LAN_I/F 17 a to the electronic device 3 a via the LAN 5.

[0295] Step ST32:

[0296] The SNMP agent 81 a realized by the CPU 27 a of the electronicdevice 3 a shown in FIG. 13 makes an access to the ROM/RAM 21 a or theHDD 22 a in response to the request received from the SNMP manager 80 avia the LAN_I/F 26 a shown in FIG. 13 in the step ST31 and prepares anentry having a status of “3 (under Creation)” as shown in FIG. 26A onthe second line in the Trap transmission destination table 42 shown inFIG. 16.

[0297] Step ST33:

[0298] The SNMP agent 81 a transmits a response “GetResponse” indicatingthat normal processing has completed from the LAN_I/F 26 a to thecomputer 2 b via the LAN 5.

[0299] Step ST34:

[0300] The SNMP manager 80 a of the computer 2 b generates a request“SetRequest” (proV1TrapDestAddress. [max(index)+1], YY. YY. YY. YY) andtransmits the same from the LAN_I/F 17 a to the electronic device 3 avia the LAN 5.

[0301] Step ST35:

[0302] The SNMP agent 81 a of the electronic device 3 a shown in FIG. 13makes an access to the ROM/RAM 21 a or the HDD 22 a in response to therequest received from the SNMP manager 80 a via the LAN_I/F 26 a shownin FIG. 13 in the step ST34 and sets “YY. YY. YY. YY” to a Traptransmission address of the second entry in the Trap transmissiondestination table 42 as shown in FIG. 26B.

[0303] Thereby, “YY. YY. YY. YY” as the IP address of the computer 2 bis automatically set to the second entry in the Trap transmissiondestination table 42.

[0304] Step ST36:

[0305] The SNMP agent 81 a transmits a response “GetResponse” indicatingthat normal processing has completed from the LAN_I/F 26 a to thecomputer 2 b via the LAN 5.

[0306] Step ST 37:

[0307] The SNMP manager 80 a of the computer 2 b generates a request“SetRequest” (proV1TrapDestEntryStatus. [max(index)+1], 1) and transmitsthe same from the LAN_I/F 17 a to the electronic device 3 a via the LAN5.

[0308] Step ST38:

[0309] The SNMP agent 81 a makes an access to the ROM/RAM 21 a or theHDD 22 a in response to the request received from the SNMP manager 80 avia the LAN_I/F 26 a shown in FIG. 13 in the step ST37 and sets thestatus on the second line in the Trap transmission destination table 42to “1 (valid)” as shown in FIG. 26C.

[0310] Thereby, the IP address of the computer 2 b set to the Traptransmission destination table 42 becomes valid as the Trap transmissionaddress.

[0311] Step ST39:

[0312] The SNMP agent 81 a transmits a response “GetResponse” indicatingthat normal processing has completed from the LAN_I/F 26 a to thecomputer 2 b via the LAN 5.

[0313] Note that an entry including an IP address automatically set fromthe SNMP manager 80 a to the Trap transmission destination table 42 iswritten to the ROM/RAM 21 a or the HDD 22 a after the automatic settingprocessing is completely ended.

[0314] [Third Operation Example]

[0315] In this operation example, the case will be explained where anaddress change request of an address is generated from the SNMP manager80 a of the computer 2 b almost simultaneously with an address changerequest from the SNMP manager 80 a of the computer 2 a to the entry onthe first line in the Trap transmission destination table 42.

[0316]FIG. 27 is a flowchart for explaining the operation example.

[0317] Step ST41:

[0318] The SNMP manager 80 a of the computer 2 a transmits a request“GetRequest” from the LAN_I/F 17 a to the electronic device 3 a via theLAN 5 shown in FIG. 13 and confirms that the Trap transmission addressof the entry on the first line in the Trap transmission destinationtable 42 is “0. 0. 0. 0” and the status is “1 (valid)”.

[0319] Step ST42:

[0320] The SNMP manager 80 a of the computer 2 b transmits a request“GetRequest” from the LAN_I/F 17 a to the electronic device 3 a via theLAN 5 shown in FIG. 13 and confirms that the Trap transmission addressof the entry on the first line in the Trap transmission destinationtable 42 is “0. 0. 0. 0” and the status is “1 (valid)”.

[0321] Step ST43:

[0322] The SNMP manager 80 a of the computer 2 a generates a request“SetRequest” (proV1TrapDestAddress. [1], XX. XX. XX. XX) and transmitsthe same from the LAN_I/F 17 a to the electronic device 3 a via the LAN5.

[0323] Step ST44:

[0324] The SNMP agent 81 a of the electronic device 3 a makes an accessto the ROM/RAM 21 a or the HDD 22 a in response to the request receivedfrom the SNMP manager 80 a of the computer 2 a via the LAN_I/F 26 ashown in FIG. 13 in the step ST43 and changes the Trap transmissionaddress of the first entry in the Trap transmission destination table 42shown in FIG. 16 to “XX. XX. XX. XX”.

[0325] Thereby, “XX. XX. XX. XX” as an IP address of the computer 2 a isautomatically set to the first entry in the Trap transmissiondestination table 42.

[0326] Step ST45:

[0327] The SNMP agent 81 a transmits a response “GetResponse” indicatingthat normal processing has completed from the LAN_I/F 26 a to thecomputer 2 a via the LAN 5.

[0328] Step ST46:

[0329] Continuously, the SNMP manager 80 a of the computer 2 b generatesa request “SetRequest” (proV1TrapDestAddress. [1], YY. YY. YY. YY) andtransmits the same from the LAN_I/F 17 a to the electronic device 3 avia the LAN 5.

[0330] Step ST47:

[0331] The SNMP agent 81 a transmits a response “GetResponse” indicatingan error from the LAN_I/F 26 a to the computer 2 b via the LAN 5.

[0332] As explained above, according to the communication system 1 a,even when an address change request of an address is generated from theSNMP manager 80 a of the computer 2 b almost simultaneously with anaddress change request from the SNMP manager 80 a of the computer 2 a tothe entry on the first line in the Trap transmission destination table42, the IP address of the computer 2 a which generated the addresschange request first can be set as the Trap transmission address and theaddress change request of the computer 2 b made after that can beprocessed as an error.

[0333] [Fourth Operation Example]

[0334] In this operation example, the case where an adding request of anentry on the second line in the Trap transmission destination table 42is generated from the computer 2 b almost simultaneously with that fromthe computer 2 a will be explained.

[0335]FIG. 28 is a flowchart for explaining the operation example.

[0336] Step ST51:

[0337] The SNMP manager 80 a of the computer 2 a generates a request“SetRequest” (proV1TrapDestEntryStatus. 2, 2) from the LAN_I/F 17 a tothe electronic device 3 a via the LAN 5 and transmits the same from theLAN_I/F 17 a to the electronic device 3 a via the LAN 5.

[0338] Step ST52:

[0339] The SNMP agent 81 a of the electronic device 3 a makes an accessto the ROM/RAM 21 a or the HDD 22 a in response to the request receivedfrom the SNMP manager 80 a of the computer 2 a via the LAN_I/F 26 ashown in FIG. 13 in the step ST51 and adds a second entry in the Traptransmission destination table 42 shown in FIG. 16.

[0340] Step ST53:

[0341] The SNMP agent 81 a transmits a response “GetResponse” indicatingthat normal processing has completed from the LAN_I/F 26 a to thecomputer 2 a via the LAN 5.

[0342] Step ST54:

[0343] Continuously, the SNMP manager 80 a of the computer 2 b generatesa request “SetRequest” (proV1TrapDestEntryStatus. 2, 2) from the LAN_I/F17 a to the electronic device 3 a via the LAN 5 shown in FIG. 13 andtransmits the same from the LAN_I/F 17 a to the electronic device 3 avia the LAN 5.

[0344] Step ST55:

[0345] The SNMP agent 81 a of the electronic device 3 a transmits aresponse “GetResponse” indicating an error from the LAN_I/F 26 a to thecomputer 2 b via the LAN 5 in response to a request received from theSNMP manager 80 a of the computer 2 b via the LAN_I/F 26 a shown in FIG.13 in the step ST51.

[0346] As explained above, according to the communication system 1 a, inthe case where an adding request of the second entry in the Traptransmission destination table 42 is generated from the computer 2 balmost simultaneously with that from the computer 2 a, entry addingprocessing can be performed for the request from the computer 2 a andthe request from the computer 2 b can be processed as an error.

[0347] [Fifth Operation Example]

[0348] In this operation example, the case where abnormality or apredetermined event occurs in the electronic device 3 a, consequently,the electronic device 3 a needs to transmits a Trap to the computers 2 aand 2 b will be explained.

[0349]FIG. 29 is a flowchart for explaining the operation example.

[0350] Step ST61:

[0351] When the SNMP agent 81 a realized as a result that the CPU 27 aof the electronic device 3 a shown in FIG. 13 executes a program judgesthat a state satisfying a condition to transmits a Trap is obtained inthe electronic device 3 a, it proceeds to processing in the step ST62.

[0352] Step ST62:

[0353] The SNMP agent 81 a judges whether the Trap transmission addressset to the first line in the Trap transmission destination table 42 is“0. 0. 0. 0” or not and proceeds to processing of the step ST63 whenjudged to be “0. 0. 0. 0” while not, proceeds to processing of the stepST64.

[0354] Step ST63:

[0355] The SNMP agent 81 a ends the processing without transmitting aTrap.

[0356] Step ST64:

[0357] The SNMP agent 81 a judges whether or not the status of the entryon the first line in the Trap transmission destination table 42 is “5(fixed)” or “1 (valid)” and proceeds to processing of the step ST65 whenjudged to be “5 (fixed)” or “1 (valid)”, while not, proceeds toprocessing of the step ST66.

[0358] Step ST65:

[0359] The SNMP agent 81 a reads a Trap transmission address stored inthe entry on the first line in the Trap transmission destination table42 and transmits a Trap from the LAN_I/F 26 a to the computer 2 a or 2 bvia the LAN 5 shown in FIG. 13 by using the Trap transmission address asan address.

[0360] Step ST66:

[0361] The SNMP agent 81 a judges whether a next line (entry) exists inthe Trap transmission destination table 42 or not and proceeds toprocessing of the step ST67 when judged existing, while not, ends theprocessing.

[0362] Step ST67:

[0363] The SNMP agent 81 a judges whether the status of the next line inthe Trap transmission destination table 42 is “5” or “1” and the Traptransmission address is not “0. 0. 0. 0”, and proceeds to processing ofthe step ST68 when judged to be not “0. 0. 0. 0”, while otherwise,returns to processing of the step ST66.

[0364] Step ST68:

[0365] The SNMP agent 81 a reads a Trap transmission address stored inan entry on the above mentioned next line in the Trap transmissiondestination table 42 and transmits a Trap from the LAN_I/F 26 a to thecomputer 2 a or 2 b via the LAN 5 shown in FIG. 13 by using the Traptransmission address as an address.

[0366] As explained above, according to the communication system 1 a,the IP address of the computers 2 a and 2 b as a transmissiondestination of the Trap can be automatically set to the electronicdevice 3 a, so a trouble of a user can be reduced.

[0367] Also, according to the communication system 1 a, even in the casewhere a request of adding entry or writing an address in the Traptransmission destination table 42 is generated from a plurality ofcomputers 2 a and 2 b to the electronic device 3 a, processing can beappropriately performed in an order the requests are received.

[0368] The present invention is not limited to the above embodiments.

[0369] For example, in the above embodiments, the case where onecomputer 2 and one electronic device 3 were connected to the LAN 5 asshown in FIG. 1 and the case where two computers 2 a and 2 b and oneelectronic device 3 a were connected to the LAN 5 as shown in FIG. 12were explained as examples, but the number of the electronic devices andthe computers connected to the LAN 5 may be any.

INDUSTRIAL APPLICABILITY

[0370] The present invention can be applied to an electronic devicemonitoring method, etc. for performing processing of monitoring andmaintenance of an electronic device connected via a network, such as adomestic LAN and the Internet.

1. An electronic device maintenance method for performing maintenance ofan electronic device by a computer via a network, comprising: a firststep that said computer obtains remote maintenance management dataindicating a communication protocol used in a communication relating tomaintenance of said electronic device from said electronic device viasaid network; and a second step that said computer performs processingrelating to maintenance of said electronic device by performing acommunication with said electronic device by using said communicationprotocol indicated by said remote maintenance management data obtainedin said first step.
 2. An electronic device maintenance method as setforth in claim 1, further comprising a third step that, when connectionby said electronic device to said network is recognized, said computerobtains identification data of the recognized electronic device on saidnetwork; and in said second step, said computer performs saidcommunication with said electronic device by further using saididentification data obtained in said third step.
 3. An electronic devicemaintenance method as set forth in claim 1, wherein in said first step,said computer obtains from said electronic device said remotemaintenance management data indicating correspondence between a kind ofone or a plurality of functions relating to said maintenance and saidcommunication protocol used in communication relating to the function;and in said second step, said computer performs communication relatingto said specified kind of function by using said communication protocolcorresponding to said specified kind of function with said electronicdevice based on said remote maintenance management data.
 4. Anelectronic device maintenance method as set forth in claim 3, wherein insaid second step, said computer displays on a display means of saidcomputer a screen for allowing to specify said function indicated bysaid remote maintenance management data and performs a communicationwith said electronic device relating to said specified function inaccordance with said screen.
 5. An electronic device maintenance methodas set forth in claim 1, wherein in said first step, said computerobtains from said electronic device said remote maintenance managementdata indicating correspondence between a kind of a plurality offunctions relating to said maintenance, said communication protocol usedin a communication relating to said respective plurality of functions,and use authorization data regulating respective use authorization ofsaid plurality of functions; and in said second step, said computerperforms a communication relating to said specified function by usingsaid communication protocol corresponding to said specified kind of saidfunction with said electronic device based on said remote maintenancemanagement data.
 6. An electronic device maintenance method as set forthin claim 1, wherein in said first step, said computer obtains from saidelectronic device said remote maintenance management data furtherindicating path specification data indicating a path to a directorystoring data or a program relating to said maintenance in a memory meansof said electronic device; and in said second step, said computerspecifies a path indicated by said path specification data in saidmemory means and makes an access to said memory means based on saidremote maintenance management data.
 7. An electronic device maintenancemethod as set forth in claim 1, further comprising a fourth step thatsaid electronic device transmits condition data indicating a conditionof the electronic device to said computer via said network; and a fifthstep that said computer display on a display means a screen inaccordance with said condition data received in said fourth step.
 8. Anelectronic device maintenance method as set forth in claim 1, furthercomprising a sixth step that said computer automatically writes to saidelectronic device identification data for identifying the computer on anetwork as transmission destination data; and a seventh step that saidelectronic device transmits an interruption signal to said computer byusing said transmission destination data written in said sixth step whenthe electronic device becomes a predetermined condition.
 9. Anelectronic device maintenance method as set forth in claim 8, wherein insaid seventh step, said electronic device notifies to said computer saidpredetermined condition together with said interruption signal.
 10. Anelectronic device maintenance method as set forth in claim 8, furthercomprising an eighth step that said electronic device stores status dataindicating whether the transmission destination data can be rewritten bymaking to correspond to said transmission destination data written insaid sixth step; and a ninth step that said computer rewrites saidtransmission destination data corresponding to said status data under acondition that the status data indicates that rewriting is possible. 11.An electronic device maintenance method as set forth in claim 10,wherein in said eighth step, said electronic device stores table datahaving one or a plurality of entries composed of said transmissiondestination data and said status data corresponding to the transmissiondestination data; and said electronic device maintenance method furtherincludes a tenth step that said computer requires adding of said entryto said electronic device; and an eleventh step that said electronicdevice adds said new entry to said table data in response to saidrequest in said tenth step.
 12. An electronic device maintenance methodas set forth in claim 8, wherein said electronic device can be set onemode selected from a first mode for permitting to write saididentification data of said computer as said transmission destinationdata from said computer and a second mode for forbidding to write saididentification data from said computer.
 13. An electronic devicemaintenance method as set forth in claim 10, wherein in the case thatidentification data for identifying said computer on said network afterstarting up, restarting or initializing in the previous time, saidelectronic device permits said computer to write said identificationdata after changed as said transmission destination data correspondingto said status data under a condition that said status data indicatesthat rewriting is possible.
 14. A computer for performing maintenance ofan electronic device via a network, comprising: an interface forperforming a communication with said electronic device via said network;a memory means for storing remote maintenance management data indicatinga communication protocol used in a communication relating to maintenanceof said electronic device obtained from said electronic device via saidinterface; and a control means for performing processing relating tomaintenance of said electronic device by performing a communication withsaid electronic device via said interface by using said communicationprotocol indicated by said remote maintenance management data stored insaid memory means.
 15. A computer as set forth in claim 14, wherein saidcontrol means, when recognizing connection by said electronic device tosaid network, obtains identification data of the recognized electronicdevice on said network via said interface, stores the same in saidmemory means, and performs said communication with said electronicdevice by further using the identification data.
 16. A computer as setforth in claim 14, further comprising a specification means, whereinsaid memory means stores said remote maintenance management data furthercomprising maintenance function specification data indicating a kind ofone or a plurality of functions relating to said maintenance; and saidcontrol means refers to said maintenance function specification data andperforms said communication relating to a specified function among saidone or a plurality of functions indicated by the maintenance functionspecification data with said electronic device.
 17. A computer as setforth in claim 16, further comprising a display means, wherein saidcontrol means displays on said display means a screen for allowing tospecify one or a plurality of functions indicated by said maintenancefunction specification data and performs said communication relating toa function specified by said specification means with said electronicdevice in accordance with said screen.
 18. A computer as set forth inclaim 14, wherein said memory means stores said remote maintenancemanagement data further comprising use authorization data regulating useauthorization of the function for respective functions indicated by saidmaintenance function specification data; and said control means refersto said use authorization data and performs said communication relatingto the specified function with said electronic device under a conditionthat a person specified the function has use authorization of thefunction.
 19. A computer as set forth in claim 14, wherein said memorymeans stores said remote maintenance management data further includingpath specification data indicating a path to a directory storing data ora program relating to said maintenance in a memory means of saidelectronic device; and said control means refers to said pathspecification data and makes an access to said memory means of saidelectronic device by specifying a path indicated by said pathspecification data in a memory means of said electronic device.
 20. Acomputer as set forth in claim 14, further comprising a display means,wherein said interface means receives condition data indicating acondition of said electronic device from the electronic device via saidnetwork; and said control means displays on said display means a screenin accordance with said condition data.
 21. A computer as set forth inclaim 14, wherein said control means makes an access from said interfacemeans via said network to a memory means of said electronic devicestoring transmission destination data specifying a transmissiondestination of an interruption signal to be sent and writesidentification data for identifying the computer on the network as saidtransmission destination data when said electronic device becomes apredetermined condition.
 22. A computer as set forth in claim 21,wherein when said memory means of said electronic device stores statusdata indicating whether the transmission destination data can berewritten by making to correspond to said transmission destination data,said control means writes said identification data as said transmissiondestination data corresponding to the status data to said memory meansof said electronic device via said interface under a condition that saidstatus data indicates that rewriting is possible.
 23. An electronicdevice subjected to maintenance by a computer via a network, comprising:an interface for performing a communication with said computer via saidnetwork; a memory means for storing remote maintenance management dataindicating a communication protocol used in a communication relating tomaintenance by said computer; and a control means for transmitting saidremote maintenance management data to said computer via said interfaceand performs a communication relating to said maintenance with saidcomputer by using said communication protocol indicated by said remotemaintenance management data in accordance with a request from saidcomputer.
 24. An electronic device as set forth in claim 23, wherein:said memory means stores transmission destination data indicating atransmission destination of an interruption signal to be sent when saidelectronic device becomes a predetermined condition and is written bysaid computer via said interface identification data for identifying thecomputer on said network as said transmission destination data; and saidcontrol means notifies a condition of the electronic device bytransmitting said interruption signal to said computer via saidinterface based on said transmission destination data stored in saidmemory means when said electronic device becomes said predeterminedcondition.
 25. An electronic device as set forth in claim 24, whereinsaid memory means stores status data indicating whether the transmissiondestination data can be rewritten by making to correspond to saidtransmission destination data; and said control means permits saidcomputer to write identification data of the computer as saidtransmission destination data corresponding to the status data under acondition that said status data indicates that rewriting is possible.26. An electronic device as set forth in claim 25, wherein: said memorymeans stores table data having one or a plurality of entries composed ofsaid transmission destination data and said status data corresponding tothe transmission destination data; and said control means adds a newentry to said table data in accordance with the request when receiving arequest to add said entry from said computer via said interface.
 27. Anelectronic device as set forth in claim 25, wherein said control means,when identification data for identifying said computer on said networkis changed after starting up, restarting or initializing said electronicdevice in the previous time, permits said computer to write saididentification data as said transmission destination data correspondingto said status data under a condition that said status data indicatesthat rewriting is possible.
 28. An electronic device as set forth inclaim 27, wherein said control means, when transmission destination datastored in said memory means indicates a predetermined initial value andsaid status data corresponding to the transmission destination dataindicates that rewriting is possible, permits said computer to writeidentification data of the computer as said transmission destinationdata corresponding to the status data.
 29. A program executed by acomputer for performing maintenance of an electronic device via anetwork, comprising: a first step for receiving remote maintenancemanagement data indicating a communication protocol used in acommunication relating to maintenance of said electronic device fromsaid electronic device via said network; a second step for storing saidremote maintenance management data received in said first step in amemory means provided to said computer; and a third step for processingrelating to maintenance of said electronic device by performing acommunication with said electronic device via said network by using saidcommunication protocol indicated by said remote maintenance managementdata stored in said memory means.
 30. A program as set forth in claim29, further comprising: a fourth step, when recognizing connection bysaid electronic device to said network, for obtaining identificationdata of the recognized electronic device on said network via saidnetwork and stores the same in said memory means; and wherein in saidthird step, said communication is performed with said electronic deviceby further using said identification data obtained and stored in saidmemory means in said fourth step.
 31. A program as set forth in claim29, wherein in said first step, said remote maintenance management dataindicating correspondence between a kind of one or a plurality offunctions relating to said maintenance and said communication protocolused in a communication relating to the function is received from saidelectronic device via said network; and in said third step, based onsaid remote maintenance management data, a communication relating tosaid specified kind of function is performed with said electronic deviceby using said communication protocol corresponding to a specified kindof said function.
 32. A program as set forth in claim 29, wherein insaid third step, a screen for allowing to specify said functionindicated by said remote maintenance management data is displayed by adisplay means of said computer and communication relating to saidspecified function is performed with said electronic device inaccordance with said screen.
 33. A program as set forth in claim 29,wherein in said first step, said remote maintenance management dataindicating correspondence between a kind of one or a plurality offunctions relating to said maintenance, said communication protocol usedin a communication relating to said plurality of functions and useauthorization data regulating respective use authorization of saidplurality of functions is received from said electronic device via saidnetwork; and in said third step, based on said remote maintenancemanagement data, a communication relating to said specified function isperformed with said electronic device by using said communicationprotocol corresponding to said specified kind of said function under acondition that a person specified said function has use authorization ofthe function.
 34. A program as set forth in claim 29, wherein in saidfirst step, said remote maintenance management data further indicatingpath specification data indicating a path to a directory storing data ora program relating to said maintenance in a memory means of saidelectronic device is received via said electronic device via saidnetwork; and in said third step, based on said remote maintenancemanagement data, an access is made to said memory means by specifying apath indicated by said path specification data in said memory means. 35.A program as set forth in claim 29, further comprising a fourth step formaking an access via said network to a memory means of said electronicdevice for storing transmission destination data indicating atransmission destination of an interruption signal to be sent when saidelectronic device becomes a predetermined condition and writesidentification data for identifying said computer on the network as saidtransmission destination data.
 36. A program as set forth in claim 35,wherein in said fourth step, in the case where said memory means of saidelectronic device stores status data indicating whether the transmissiondestination data can be rewritten by making to correspond to saidtransmission destination data, said identification data of said computeris written to a memory means of said electronic device as saidtransmission destination data corresponding to said status data under acondition that the status data indicates that rewriting is possible. 37.A program executed in an electronic device subjected to maintenance by acomputer via a network, comprising a first step for transmitting to saidcomputer via said network remote maintenance management data indicatinga communication protocol used in a communication relating to maintenanceof said electronic device with said computer; and a second step forperforming communication relating to said maintenance with said computerby using said communication protocol indicated by said remotemaintenance management data.
 38. A program as set forth in claim 37,further comprising: a third step that identification data of saidcomputer on said network is written to a memory means of said electronicdevice by said computer as transmission destination data of aninterruption signal; and a fourth step for transmitting saidinterruption signal to said computer by using the transmissiondestination data stored in the memory means of said electronic device insaid third step when said electronic device becomes a predeterminedcondition.
 39. A program as set forth in claim 38, wherein in said thirdstep, status data indicating whether the transmission destination datacan be rewritten is stored in said memory means by making to correspondto said transmission destination data; and said program furthercomprises a fifth step, under a condition that said status dataindicates that rewriting is possible, for permitting said computer towrite identification data of the computer as said transmissiondestination data corresponding to the status data.
 40. A program as setforth in claim 38, further comprising a sixth step, in the case saidmemory means stores table data having one or a plurality of entriescomposed of said transmission destination data and said status datacorresponding to the transmission destination data, when receiving arequest for adding said entry from said computer, for adding said newentry to said table data in response to the request.
 41. A program asset forth in claim 38, further comprising a seventh step, whenidentification data for identifying said computer on said network ischanged after starting up, restarting or initializing said electronicdevice in the previous time, for permitting said computer to write saididentification data as said transmission destination data correspondingto said status data under a condition that said status data indicatesthat rewriting is possible.
 42. A program as set forth in claim 41,wherein in said seventh step, when transmission destination data storedin said memory means indicates a predetermined initial value and saidstatus data corresponding to the transmission destination data indicatesthat rewriting is possible, writing identification data of said computeras said transmission destination data corresponding to the status datais permitted to said computer.